Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BA Plan & log transaction #54

Closed
wants to merge 1 commit into from

Conversation

nirbar
Copy link
Contributor

@nirbar nirbar commented Apr 27, 2021

No description provided.

@nirbar nirbar force-pushed the nirbar-5386-plan-log branch from 652f7fa to d3c3fd1 Compare April 27, 2021 08:56
Copy link
Contributor

@rseanhall rseanhall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's frustrating that you're ignoring my reviews. I don't know why you're insisting to put all these changes in one commit in one PR.

src/engine/apply.cpp Outdated Show resolved Hide resolved
src/engine/apply.cpp Show resolved Hide resolved
{
DWORD cbSize;
LPCWSTR wzTransactionId;
BOOL fTransaction;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MSIHANDLE hMsiTrns = NULL;
HANDLE hMsiTrnsEvent = NULL;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you insisting on these changes?

LogId(REPORT_STANDARD, MSG_MSI_TRANSACTION_BEGIN, pRollbackBoundary->sczId);

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you insisting on these changes?

Comment on lines -3070 to +3066
PackageFindRollbackBoundaryById(pPackages, sczId, &pRollbackBoundary);
ExitOnFailure(hr, "Failed to find rollback boundary: %ls", sczId);

pRollbackBoundary->sczLogPath = sczLogPath;

hr = MsiEngineBeginTransaction(pRollbackBoundary);
hr = MsiEngineBeginTransaction(szName, &hMsiTrns, &hMsiTrnsEvent, sczLogPath);
ExitOnFailure(hr, "Failed beginning an MSI transaction");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you insisting on these changes?

src/engine/logging.cpp Show resolved Hide resolved
Comment on lines -1026 to +1029
__in BURN_ROLLBACK_BOUNDARY* pRollbackBoundary
__in LPCWSTR wzName,
__out MSIHANDLE *phTransactionHandle,
__out HANDLE *phChangeOfOwnerEvent,
__in_z LPCWSTR szLogPath
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you insisting on these changes?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My comment here was partially about functionality and partially about aesthetics: #29 (comment). Unfortunately, it seems like I didn't do a good job about helping you understand that I made the aesthetical changes myself. So you ended up spending a lot of time fighting merge conflicts to bring your changes back here. The end result is you are reverting the aesthetical changes I made while not implementing any more functionality.

I guess it's up to you whether to spend the time to undo them, but these are the kind of changes that make it so I have to manually merge your PR. Since manually merging takes a lot more time, it would have to wait until I'm interested in doing that. I hope you understand that, and I hope you will consider contributing your other v3 changes even if this PR doesn't get merged any time soon.

BOOL fTransaction;
BOOL fActiveTransaction; // only valid during Apply.
LPWSTR szLogPathVariable;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be sczLogPathVariable.

Comment on lines +912 to +914
hr = WiuInitialize();
NativeAssert::Succeeded(hr, "Failed to initliaze wiutil.");

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you insisting on these changes? #29 (comment)

@nirbar
Copy link
Contributor Author

nirbar commented Apr 27, 2021

I'm not insisting on anything. Rather, I got lost with all the changes you're insisting on and simply pushed what I had.
I made a lot of effort with all these back and forth pull requests and this kind of attitude really isn't helping.
I made these changes in WiX3 at the requests of my clients, and agreed to port them to v4 because you asked me to. However since you're very particular on how you want every line code to look like and on splitting to distinct pull requests I think it will be easier for both of us if you do it yourself.
I'm sure you have good reasons for being this particular. However one may argue that in large open source projects a maintainer could be a bit less restrictive about their aesthetic taste while still not compromising about functionality.
Needless to say, I don't think my programming aesthetics is any lesser or better than yours. It's just my personal preference.

@rseanhall
Copy link
Contributor

I'm sorry if I'm coming off as being hard to work with. I do appreciate what you're doing and I want your changes.

What I'm having trouble with is striking a balance between giving review comments for you to fix versus me fixing everything for you. I spent a significant amount of time a few months ago fixing your original v4 pull request from 2016. Fixing the comments that I put on that original PR. Then I spent a significant amount of time taking your previous changes.

If you don't want to spend any more time on these changes, then that's fine. They're additive so I can get to them when I have time. What I'm really interested in are your other v3 changes. Especially the breaking ones, like only allowing MsiPackage and MspPackage inside of MSI transactions.

@nirbar
Copy link
Contributor Author

nirbar commented Apr 28, 2021

I don't mind doing the PR if you don't mind focusing on functionality

@nirbar nirbar force-pushed the nirbar-5386-plan-log branch from d3c3fd1 to 72c3c75 Compare April 28, 2021 15:35
@rseanhall
Copy link
Contributor

I incorporated all of your changes into wixtoolset/wix#34. Hopefully it will be easier for you to contribute your other changes now that we're back to a single repo. Thanks.

@rseanhall rseanhall closed this Aug 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants